SUPPORT / SAMPLES & SAS NOTES
 

Support

Installation Note 46223: Configuration of the SAS® Web Infrastructure Platform might fail during the SAS® Deployment Wizard process

DetailsAboutRate It

When you use the SAS Deployment Wizard to configure the SAS Web Infrastructure Platform, the following error might occur in a separate window:

The following problem was encountered while configuring SAS Web Infrastructure Platform:

Metadata deployment failed - 
 <SAS_config_dir>\Lev1\Web\Temp/SASApplicationInstrastructure.appxml

INFO  *** ApplicationMetadataUtility started on Apr 3, 2012 ***
INFO  Server odcmsaprp021s.corp.dvn.com:8561, user sasadm@saspw.
ERROR ApplicationMetadataUtility has failed.  Error parsing source XML.
ERROR The markup declarations contained or pointed to by the document  
      type declaration must be well-formed.
ApplicationMetadataUtility completed with errors.

The webinfpltfm_configure_*.log file, located in the SAS-configuration-directory\Lev1\Logs\Configure directory, will contain the previous messages as well as the following messages:

[echo] Log saved to 
       <SAS_config_dir>\Lev1\Logs\Configure\CreateApplicationMetadata.log
[echo] Return Code: 8
[propertyfile] Updating property file: 
     <SAS_config_dir>\Lev1\Logs\Configure\webinfpltfm_config_status.properties
[echo] Metadata deployment failed - 
       <SAS_config_dir>\Lev1\Web\Temp/SASApplicationInfrastructure.appxml

BUILD FAILED
. . .more text lines. . .

The Application Metadata Utility (AMU) requires network access, so this problem occurs if your system does not have network access. To determine whether you have network access, see whether you can connect to www.w3.org successfully from a browser on your system.

If the access to the network fails, there are two workarounds:

  • Open the firewall to enable access to www.w3.org.
  • Modify the Domain Name System (DNS) so that www.w3.org resolves to a local machine inside the firewall. The local machine does not actually need to serve content nor even exist. The XML parser just needs to detect a could not connect message or a 404 error in order to work. Usually, this redirection can be done by modifying C:\Windows\System32\drivers\etc\hosts so that it includes the following:
    127.0.0.1 www.w3.org

    Including this information redirects www.w3.org requests to the local machine.

The two workarounds are temporary and can be removed as soon as the SAS Deployment Wizard configuration is complete.



Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemSAS Web Infrastructure PlatformSolaris for x649.39.3_M29.3 TS1M09.3 TS1M2
Linux for x649.39.3_M29.3 TS1M09.3 TS1M2
HP-UX IPF9.39.3_M29.3 TS1M09.3 TS1M2
64-bit Enabled Solaris9.39.3_M29.3 TS1M09.3 TS1M2
64-bit Enabled AIX9.39.3_M29.3 TS1M09.3 TS1M2
Microsoft® Windows® for x649.39.3_M29.3 TS1M09.3 TS1M2
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.